Decentralized computer systems and methods for using a debit network as an intermediary between distributed ledgers

ABSTRACT

Decentralized computer systems and methods are disclosed for using a debit network as an intermediary between distributed ledgers. One method includes: receiving, at a first blockchain network from a merchant, transaction information comprising a consumer identification, an issuer identification from a payment vehicle presented for a transaction, and a transaction amount in resources of a first type, wherein the merchant and/or its acquirer are participants of the first blockchain network but the consumer and/or issuer are not participants of the first blockchain network; sending the transaction information to a debit network; identifying, using the debit network, a second blockchain network having the consumer and/or the issuer as participants, using the received consumer identification or issuer identification; and if participants of the second blockchain network accept the transaction, generating a new immutable entry to the second blockchain network indicating a change in the resources of a second type.

FIELD OF DISCLOSURE

The present disclosure relates generally to the field of paymenttransactions and, more particularly, to decentralized computer systemsand methods for using a debit network as an intermediary betweendistributed ledgers.

BACKGROUND

Merchants often need to incentivize and track use of their merchandiseand services among their consumers. Many merchants and their acquirerstry to accomplish these goals by issuing resources that a consumer mayuse to purchase goods and/or services at other merchants. Theseresources may be distinct from the normal currency or cryptocurrencythat other merchants would typically accept from consumers for theirtransacted goods or services.

An example of this resource that merchants may use to incentivize andtrack use of merchandise and services are loyalty points. For example, amerchant may allot loyalty points to a customer when the customer uses aloyalty card to make purchases of goods or services from the merchant orthe affiliates of the merchant. In a typical scenario, the consumer canredeem the loyalty points at the specific merchant (e.g., who issued theloyalty card) via a closed loop system. Merchants may provide standalonedevices where the customers can swipe their loyalty cards to makepurchase with the loyalty points, where the loyalty cards may bephysical cards and/or a digital card linked to a phone number. However,in a traditional setting, each merchant may issue its specific resource(e.g., loyalty points) which may be restricted in use to only thatmerchant. This restriction may overwhelm the consumers because theconsumer would have to card around a payment vehicle for each resourcetype (e.g., physical loyalty card) used by each merchant, as eachmerchant may issues its own type of resource (e.g., loyalty points).Furthermore, a difficulty may also arise when a consumer would like totransact using a specific type of resource (e.g., loyalty points) atmerchants that do not typically transact in such resource, and insteadwishes to be paid in a second type of resource (e.g., currency). Forexample, a casino might issue loyalty points to a consumer for theircontinued purchase of casino products and services. The consumer maywant to occasionally shop at a merchant across the street from thecasino that may not yet directly transact using loyalty points issued bythe casino.

Therefore, there is a desire for a payment system that encouragesconsumers of a merchant to sign up for specific resources (e.g., loyaltypoints) that incentivize consumers to purchase from the merchant andhelp the merchant track the consumers' usage, while also encouragingother merchants that do not typically use the specific resource to startaccepting the specific resource.

For example, there is a desire for a payment system that may allowconsumers or patrons to earn loyalty points from online and in personactivities (e.g. shopping for goods or services, playing games atcasinos, etc.) at one or more merchants and redeem their loyalty cardpoints in a seamless manner at the merchants in and outside of thenetwork of the issuer issuing the loyalty card using existing Point ofSale (POS) solutions. Additionally, the merchants, outside the network,may need a guarantee that they will be paid when accepting loyaltypoints. Thus, in an environment where various merchants may not bemembers of the same network as entities providing, for example, loyaltypoints, there is a desire for a system and method that may act as anintermediary between these networks.

The present disclosure is directed to overcoming one or more of theseabove-referenced challenges.

SUMMARY

According to certain aspects of the present disclosure, systems andmethods are disclosed for using a debit network as an intermediarybetween distributed ledgers.

In one embodiment, a computer-implemented method is disclosed for usinga debit network as an intermediary between distributed ledgers. Themethod comprising: receiving, at a first blockchain network from a pointof sale of a merchant, transaction information comprising at least aconsumer identification, an issuer identification from a payment vehiclepresented for a transaction of a good or service, and a transactionamount in resources of a first type, wherein the merchant and/or itsacquirer are participants of the first blockchain network but theconsumer and/or issuer are not participants of the first blockchainnetwork; sending, over a wired or wireless network, the transactioninformation comprising at least the consumer identification and theissuer identification to a debit network; identifying, using the debitnetwork, a second blockchain network having the consumer and/or theissuer as participants, using the received consumer identification orissuer identification; if all of the participants of the secondblockchain network accept the transaction, generating a new immutableentry to a shared ledger of the second blockchain network indicating achange in the resources of a second type for one or more participants ofthe transaction; and sending, by the debit network, an updatedtransaction information indicating the change in the resources of thesecond type to the first blockchain network.

In the above example embodiment, the debit network may be a member ofthe first blockchain network and the second blockchain network.Furthermore, the resources of the first type may include, for example,an amount in a currency or cryptocurrency, and the resources of thesecond type may include, for example, loyalty points, or vice versa. Aconsumer may add loyalty points to the loyalty card by at least one ofearning loyalty points by purchasing goods or services provided by theissuer, transferring funds from a financial institution to the loyaltycard, and transferring points from another account. In accordance withthe above embodiment, the terms and condition associated with theaccount are at least one of spending limits on the account, markingpoints as spendable with specific merchants, and rules and regulationsaccordingly to the policies of the issuer.

The method described in the above embodiment may further include, priorto generating a new immutable entry to the shared ledger of the secondblockchain network indicating a transfer of resources, converting, usingthe second blockchain network, the transaction amount in resources ofthe first type to an amount of resources of the second type according toa conversion formula in the second blockchain network; and prompting, toparticipants of the second blockchain network, to validate whether theconsumer has the required amount of resources of the second type for thetransaction.

In the above-illustrated embodiment, the method may further include, ifall of the participants of the first blockchain network accept theupdated transaction, prompting, to participants of the first blockchainnetwork, to validate whether one or more participants of the transactionhas the required amount of resources of the first type for thetransaction; generating a new immutable entry to a shared ledger of thefirst blockchain network indicating a change in the resources of thefirst type for one or more participants of the transaction; and sending,by the first blockchain network, a transaction approved message to thepoint of sale system at the merchant.

In an another embodiment, a decentralized computer system is disclosedfor using a debit network as an intermediary between distributedledgers, the system comprising: a data storage device storinginstructions using a processor; and a processor configured to executethe instructions to perform a method including: receiving, at a firstblockchain network from a point of sale of a merchant, transactioninformation comprising at least a consumer identification, an issueridentification from a payment vehicle presented for a transaction of agood or service, and a transaction amount in resources of a first type,wherein the merchant and/or its acquirer are participants of the firstblockchain network but the consumer and/or issuer are not participantsof the first blockchain network; sending, over a wired or wirelessnetwork, the transaction information comprising at least the consumeridentification and the issuer identification to a debit network;identifying, using the debit network, a second blockchain network havingthe consumer and/or the issuer as participants, using the receivedconsumer identification or issuer identification; if all of theparticipants of the second blockchain network accept the transaction,generating a new immutable entry to a shared ledger of the secondblockchain network indicating a change in the resources of a second typefor one or more participants of the transaction; and sending, by thedebit network, an updated transaction information indicating the changein the resources of the second type to the first blockchain network.

In another embodiment, a non-transitory machine readable medium isdisclosed storing instructions that, when executed by a processor,causes the processor to perform a method for using a debit network as anintermediary between distributed ledgers, the method described in atleast some embodiments of the present disclosure.

In an example embodiment, the blockchain is accessible by at least oneof participants of the shared or distributed ledger and the processor,wherein the at least one participants of shared ledger is a differentblockchain on a network node maintained by different transactionparticipants (e.g., consumers, merchants, acquirers, issuers, etc.).Additionally, in an example embodiment, the blockchain entry comprisesat least one of a public key identifying the consumer, a unique privatekey, a header, and content data.

In an example embodiment, the processor is an observer of the blockchainand the participants of the shared ledger are validators of thetransaction. Additionally, the blockchain validators and the observerexpose standard hypertext transfer protocol (HTTP) based applicationprogram Interfaces (APIs). In the above embodiment, the attributes ofthe transaction information may be one or more of an identifier of themerchant; an identifier of the consumer; an account information of themerchant; an itemization of the goods and/or services transacted for; atransaction amount; any geographical and/or temporal information of thetransaction; any taxes, tips, and/or gratuities; any fees directedtowards acquirers, issuers, payment networks; currency exchange rates;and any other pertinent features of the payment transaction.

In another embodiment, the shared or distributed ledger is sharedbetween network nodes associated with different issuers participating inthe loyalty program, wherein each network node associated with an issuerkeeps its blockchain separate from other network nodes. In theaccordance with the above embodiment, the funds for the pendingtransaction(s) are transferred from a liquidity pool.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages on the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the detailed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a blockchain loyalty points payment system for paymenttransactions using loyalty points, in accordance with non-limitingembodiments.

FIG. 2 depicts a detailed schematic of components of the blockchainloyalty points payment system, in accordance with non-limitingembodiments.

FIG. 3 depicts a simplified sequence flow diagram of a method forefficient loyalty points payment system of FIG. 1 using blockchain, inaccordance with non-limiting embodiments.

FIG. 4 is an exemplary structure of a blockchain entry according to oneor more non-limiting embodiments.

FIG. 5 depicts a blockchain loyalty points payment system involvingmultiple blockchains for payment transactions using loyalty points.

FIGS. 6A-6B depict block diagrams of a general method for using a debitnetwork as an intermediary between distributed ledgers.

DETAILED DESCRIPTION

Various non-limiting embodiments of the present disclosure will now bedescribed to provide an overall understanding of the principles of thestructure, function, and use of systems and methods disclosed herein forestablishing a loyalty points payment system using blockchain.

As described above, merchants seek ways to incentivize spending andtrack usage of their customers, one way being through the issuance of aspecific alternative resource for spending (e.g., loyalty points).Difficulties arises when a consumer would like to spend such resourceswith other merchants who may not issue or traditionally accept thealternative resource. Furthermore, if the other merchants were to acceptthe alternative resource for spending (e.g., loyalty points by theissuing merchant), the other merchants would need some way to guaranteethat they would be paid in a resource they may be more used to (e.g.,currency (e.g., dollars, pounds, euros, etc.).

Furthermore, existing methods of payment processing of such alternativeresources (e.g., loyalty points) may be complicated, lengthy, andcumbersome for issuers, consumers, merchants, and/or acquirers.Consumers may have to carry multiple cards (e.g., each card for aspecific resource issued by one or more merchants) and remember to usethe resources while purchasing at the specific merchant. Merchant mayadditionally have to issue and manage distinct resources (e.g., loyaltypoints) to consumers. In addition, the other merchants that may allowthe usage of these resources (e.g., loyalty points) may not be in thesame network as the entities (e.g., original merchant or issuer) thatissues or facilitate the transfer of the specific resources (e.g.,loyalty points) to the consumer. There is thus a desire for a system andmethod for an intermediary between these various networks. This systemmay result in less intermediaries between the various transactionsoccurring in a loyalty points payment system, may allow transactionrecords to be written to an immutable ledger, and may allow conversioninformation to be used to facilitate translation to different pointstypes and currencies.

Thus, the embodiments of the present disclosure are directed to a systemand method for enabling merchants and consumers to manage and usemultiple resources (e.g., loyalty points and normal currency) in anefficient, transparent, and standardized, reducing costs for parties,and minimizing risks, e.g., by using a debit network as an intermediary.In various embodiments, a blockchain may refer to an open, distributedledger (e.g., “shared permissioned ledger”) that can record transactionsbetween parties to a payment transaction efficiently and in a verifiableand a permanent way (e.g., by providing visibility or by beingtransparent to various participants of the blockchain). A blockchain maybe operated by many different parties that come to share consensus. Itmay maintain a growing list of ordered records, called blocks. Eachblock may have a timestamp and a link to a previous block. Records maynot be altered retroactively. A common analogy for a blockchain may be adigital network of safety deposit boxes. These boxes can secure anydigital asset (e.g., currency, securities, loyalty points, contracts).Each box may be locked with a crypto private key. The owner of the boxcan use their key to unlock the box and push a digital asset to anothersafety deposit box that is secured by the keys of the recipient. Therecipient can then retrieve the digital asset from their safety depositbox.

A blockchain may include one or more of the following features. In someembodiments, a blockchain may include a database, and tabular schemesmay be used to encode core data types on top of a traditional database.In such embodiments, tables may consist of blocks, which may be bundlesof transactions. Furthermore, such embodiments may be configured so thatblockchain transactions may be all or nothing. A blockchain may berendered immutable, ensuring that the data stored cannot be changed.Each block in the chain may include reference to the previous block sothat in chains with a high rate of new transactions, the block maybecome securely linked to previous blocks. The block may also bereplicated numerous times. Cryptography may ensure that users of ablockchain may only edit the parts of the blockchain that they “own” bypossessing the private keys necessary to write to the file. Cryptographymay also ensure that copies of the distributed blockchain are kept insync. Distributed ledgers (“shared ledgers”) may be used for transactionintegrity. Thus, ledgers may be maintained by multiple independententities on different computing devices. A consensus protocol may befollowed by each entity to maintain a consistent view of the ledger.Distributed ledgers provide for greater resiliency against maliciousattacks or system failures. Furthermore, a blockchain may be“permissioned”—e.g., allow access to only a specific set ofparticipants. It is contemplated that it may be useful for financialapplications to use distributed, centralized, permissioned, tokenlessledgers as a basis for the implementations of various systems andmethods presented herein.

Blockchain may have a long-term impact on the financial servicesindustry in paring down transaction settlement time from days to minutesand minimizing the need for intermediaries. Furthermore, it may enablepoint-to-point exchanges of digital assets without a need for trustbetween the parties in the exchange. This may eliminate the need forthird party engagement in transactions and may reduce the costs involvedin verifying a transaction.

As applied to at least some embodiments presented therein, a blockchainhaving a shared permissioned ledger may be available to participants andmay provide visibility to the participants of the blockchain, which maybe the parties of a payment transaction initiated by a consumer andoriginating at a merchant. These parties may include, but are notlimited to, the consumer, the merchant at which the transactionoriginates, the merchant's acquiring bank or institution, and theissuing institution or bank of the consumer. A blockchain process, e.g.,as described by various embodiments of the present disclosure, mayfacilitate a transparent, rules-based, communication process to reducecosts for both merchants and acquirer.

The types of blockchain systems used for payment transactions mayinclude, for example, public blockchains, private blockchains, or ahybrid form of a public and private blockchain (e.g., a consortiumblockchain or hyperledger blockchain). In a consortium blockchain, theconsortium may include and may be accessible to the participants of theblockchain (e.g., consumers, issuers, merchants, and/or acquirers of apayment transaction). A consortium blockchain may proffer the benefitsof setting control of the rules for payment transaction using loyaltypoints within the bounds as agreed upon by the participants. Thus, therights to read and/or access the blockchain may be restricted todifferent participants, based on individual classes or identities of theparticipants.

In some embodiments, the participants of a blockchain, prior to joiningthe blockchain, may be vetted, and hence may not be anonymousparticipants. Vetting may minimize the risk of any form of maliciousattacks on the blockchain. In other embodiments, the new entrants to ablockchain may be restricted to those known by other known participantsof the blockchain. These blockchains (e.g., a consortium blockchain) mayeliminate and/or significantly reduce the risks of attacks that areprevalent, for example, in public blockchains (e.g., 51% attack). Therisks may be eliminated and/or significantly reduced due to restrictionsplaced on the entry of new members. The transactions may resemble the“colored pin” approach of transferring ownership to differentparticipants in the blockchain. It may also be efficient to use certainblockchains (e.g., consortium blockchains) due to the limited number ofnodes that may need to be updated and the limited role of verifying theblocks before those are appended to the blockchain.

The members or participants of the blockchain may be represented asnodes of the blockchain. In some embodiments, for example, where thenodes may be “trusted” and/or be well connected, a blockchain may enablethe nodes to easily spot and/or fix any failures or inconsistencies ofthe blockchain. For example, in a consortium blockchain, paymenttransactions may be many degrees cheaper compared to theirimplementation on a public blockchain. Additionally or alternatively, ablockchain may be used that may provide flexibility to develop on theblockchain infrastructure. For example, a Hyper-ledger may bespecifically built to expand to other non-traditional use-cases of theblockchain. Since verification may be needed by a comparatively largernumber of nodes in the public blockchain as compared to a consortium orprivate blockchain, a public blockchain may require a high level ofcomputational power than a consortium or private blockchain.

In some embodiments, the blockchain loyalty points payment process mayinvolve a Smart Contracts application. In various embodiments, “SmartContracts” may refer to a computerized transaction protocol thatfacilitates, verifies, and/or enforces the negotiation or performance ofa contract (e.g., as the one governing a payment transaction usingloyalty points). A Smart Contract may satisfy common contractualconditions (e.g., payment terms, liens, confidentiality, enforcement,etc.), minimize malicious and/or accidental exceptions, and/or minimizethe need for trusted intermediaries. Different types of algorithms maybe employed to offer finality (e.g., of a contract) in a shortertimeframe. Various rules for initiating or managing the loyalty pointsand payment settlements between parties can be “codified” into the smartcontract between the participants. In some embodiments, once the ruleshave been “codified” into the blockchain, the rules of the SmartContracts may be rendered or configured to be final and/or immutableduring its execution of the Smart Contract.

For example, the blockchain loyalty points payment process may begoverned and/or at least initialized using Smart Contracts. Participantsof the loyalty points payment process (e.g., consumers, issuers,merchants, acquirers, etc.,) may establish the underlying attributes ofthe contract governing the payment transaction, or the underlying rulesof the loyalty points payment process. Smart Contracts may then proceedto execute the payment transaction based on the underlying attributevalues or facilitate the loyalty points payment process using theunderlying rules.

In some embodiments, cryptographic assurances may be available to theparticipants. Documents may be captured and securely stored by theblockchain, for example, in an off-the-blockchain storage (e.g. NoSQLdatabase), for retrieval by the other party. Identifiers to thesedocuments may be stored in the blockchain. These documents may include,for example, receipts of purchases, identification information of theconsumer, merchant, issuer, or acquirer, available funds or resources,geographical information, or temporal information. One or more examplesof these non-limiting embodiments are illustrated in the selectedexamples disclosed and described in detail with reference made to FIGS.1-5 in the accompanying drawings. Those of ordinary skill in the artwill understand that systems and methods specifically described hereinand illustrated in the accompanying drawings are non-limitingembodiments. The features illustrated or described in connection withone non-limiting embodiment may be combined with the features of othernon-limiting embodiments. Such modifications and variations are intendedto be included within the scope of the present disclosure.

FIG. 1 depicts an illustration of the environment for using a debitnetwork as an intermediary between distributed ledgers 100, inaccordance with non-limiting embodiments. At a high level, theenvironment comprises: a consumer 102 equipped with a payment vehicle104 from an “issuer” 116; a merchant 106 with an acquiring bank orinstitution, i.e., “acquirer” 108; a blockchain management server 112(“blockchain server”) or computing system; and a computing system orserver 114 (“payment network server”) for a payment network used in thetransaction. In various embodiments of the present disclosure, theacquirer 108 and the issuer 110 may also refer to the computing systemor server of the acquirer 108 or issuer 110, respectively.

Various embodiments of the present disclosure may involve the consumer102 conducting a payment transaction with merchant 106 using a paymentvehicle 104, e.g., a credit card with loyalty points, casino loyaltycard, etc. It will be appreciated by those of skill in the art thatconsumer 102 may present payment vehicle 104 at a POS terminal ofmerchant 106 to initiate a payment transaction. However, in someembodiments, there may be an online portal of a merchant for theconsumer to initiate a payment transaction in lieu of a physical POSterminal. Upon initiation of the payment transaction by a consumer, themerchant and/or the POS terminal of the merchant may transmittransaction information to the acquirer 108 of the merchant. Thetransaction information may include, for example, informationidentifying the issuer 110 of the payment vehicle 104 of the consumer102. The transaction information may be encrypted and entered into ablockchain where the members of a shared ledgers (e.g., nodes) may beable to read and/or access each block of the blockchain.

FIG. 2 depicts a block diagram of an example of the payment system ofFIG. 1 for using a debit network as an intermediary between distributedledgers, in accordance with non-limiting embodiments. Specifically, thenetwork includes the payment vehicle 206 of a consumer, a consumerdevice 204 of a consumer, the merchant 208, the acquirer 210, a serveror computing system that manages the use of a debit network as anintermediary between blockchain networks or their distributed ledgers(“blockchain server”) 212, the payment network server 214, and thefinancial institution(s) 216.

The payment vehicle 206 may be linked with a loyalty points account ofresources or funds defined by an account identifier (e.g., “primaryaccount number (PAN)”) and issuer identifier 206A. In one embodiment,the PAN may identify one or more payment source accounts of theconsumer, issued or established by a given issuer 202. Unless otherwisespecified herein, a payment vehicle 206 may include a physical cardincluding a plastic or metallic card having a magnetic stripe, bar code,or other device or indicia indicative of an account number or otheraccount information, and/or a virtual card, such as a display or screenshot for a mobile phone or for another portable device (e.g., a flashdrive, smart chip, a laptop or portable computer), or for a computerdevice (e.g., a desktop computer) in combination with data indicative ofan account number or other account indicative information. It is alsocontemplated that the payment vehicle 206 may have multiple embodimentsor forms. For example, payment vehicle 206 can be a physical card (e.g.,in the form of magnetic striped plastic card), a virtual card (e.g., inthe form of a display on a smart phone), or both. The virtual card maybe communicated by displaying a display or screen shot, and/or bytransmitting a signal, such as by using NFC (Near Field Communication)technology or other secure transport technologies to complete thetransaction with the selected merchants. Optionally, the virtual cardmay have a display element (e.g., a bar code or string of numbers) whichidentifies the account number (e.g., PAN) associated with the card.Alternatively, the virtual card may have display elements relating tothe merchants that accept the card.

A consumer, sometimes referred to as the end user, a cardholder, or acard member, may provide identifying information, e.g., via the PAN ofthe user, to the POS system 208A of the merchant 208 to initiate atransaction with merchant 208 using the consumer's payment vehicle 206.In some cases, the consumer may use a computing device or mobile device(“consumer device” 204) to initiate the transaction, such as for acard-not-present transaction at an online merchant. Thus, paymentvehicle 206 may enable the consumer to initiate a transaction withmerchant 208 using the payment source associated with the issuer 202that issued the payment vehicle 206 to the consumer. A consumer may alsouse the consumer device 204 to oversee, manage, or access detailsregarding a payment transaction via user interface, such as consumer GUI204A.

In various embodiments described herein, a merchant 208 may refergenerally to any type of retailer, service provider, or any other typeof business that is in networked communication with the computing systemof an acquiring institution or bank (“acquirer” 210) and uses thepayment processing services of acquirer 210. Payment processing servicesmay include receiving and responding to authorization requests as wellas facilitating the settlement of funds associated with card-basedtransactions occurring at merchant 208. In some embodiments, asdescribed herein, the acquirer 210 may use the blockchain server 212 tofacilitate the settlement of funds associated with the card-basedtransactions occurring at merchant 208. A merchant 208 may have one ormore POS systems 206A. In various embodiments described herein, a POSsystem 206A may refer broadly to include POS systems at brick and mortarlocations and “virtual” POS systems that can be associated with onlineretailors or “in-app” purchases. In some cases, a POS system 208A mayinclude a physical terminal, or other network computing system used tofacilitate a payment transaction at a location of merchant 208. Each POSsystem 208A may be generally unmodified or “stock” and simply facilitatethe standard transmission of transaction-related information to theacquirer computing system 210, as is known in the art. Thetransaction-related information may include, but is not limited to, atransaction authorization request (“authorization request”), includingbut not limited to, a payment amount, loyalty points amount, a date, atime, an account identifier, as well as other types of identifyingindicia (e.g., merchant identification). The identifying indicia mayvary based on POS system 208A, the type of merchant, and the type oftransaction, but example types of identifying indicia may include any ofthe following: an alternative identifier to the account identifier ofthe user; a user's name or other user identifier; a merchantidentification (MID) identifier; a merchant category code (MCC)identifier; a media access control (MAC) identifier; an internetprotocol (IP) identifier; a geographic identifier; and/or a payment typeidentifier.

Referring now to acquirer computing system 210, authorization interface210A may receive a transaction authorization request from POS system208A of merchant 208. The authorization request may comprise variousdata, including, for example, a MID, a MCC, the cardholder's accountidentifier 206A, and a transaction amount, among other things. In someembodiments, acquirer computing system 210 may also receive otherconsumer-identification related data, e.g., an email address, an IPaddress, etc. In yet another embodiment, the transaction authorizationrequest detail may contain identifying information about the merchant.Once the authorization request is received, acquirer 210 may transmitthe transaction authorization request, including the amount of fundsrequired for the transaction (“transaction amount”) and the accountidentifier (or issuer identifier) 206A of the user, received from POSsystem 208A, to payment network 214 for further processing of thepayment transaction. In some embodiments, a component of acquirercomputing system 210 (e.g., authorization interface 210A) may alsotransmit data identifying the acquirer to payment network 214. Stillreferring to FIG. 2 , once the transaction authorization request isdelivered to the acquirer 210, the acquirer may further query theblockchain server 212 to further process the transaction. For example,the acquirer may query one or more shared ledger participants aboutapproval of the transaction.

In various embodiments described herein, an issuer 202 may refer to aninstitution or organization that issues a payment vehicle 206 to theconsumer or to the computing system of the institution or organization.The issuer 202 may enable the consumer to use funds from a paymentsource held by the issuer (e.g. loyalty points). For example, the issuer202 may be a merchant (e.g. casino) that gives out loyalty points to theconsumer. In one embodiment, at least some of the consumer data as itpertains to a payment transaction may be stored in a shared ledger of ablockchain, where the participants of the blockchain include the partiesinvolved in the payment transaction (e.g., consumer, merchant, issuer,acquirer, etc.). In some embodiments, the transaction authorizationrequest made by the acquirer 210 may itself be a block in a blockchain,accessible to the issuer (and other participants of the blockchain) onthe shared ledger.

Once the shared ledger approves the transaction, the acquirer may sendrequest to the identified blockchain to withdraw the points. Onceloyalty points are withdrawn, a new entry may be published in theblockchain so that participants of the blockchain (e.g., merchant,acquirer, consumer, issuer, etc.) may be informed. The blockchain server212 may oversee the loyalty points transaction process when one or moreparticipants of the blockchain an attribute of the payment transaction(“transaction information”) posted on the shared ledger. The attributesmay include, but are not limited to: the identity of the merchant,consumer, acquirer, or issuer of the payment transaction; thetransaction amount; an itemization and description of the goods and/orservices transacted for; any geographical and/or temporal information ofthe payment transaction; any taxes, any tips, any discounts; any feesdirected towards acquirers, issuers, payment networks; currency exchangerates; etc. In some embodiments, any data for an attribute of thetransaction information posted to a blockchain may be encrypted usingencoder 212A, for example, to provide security and/or protect sensitiveinformation. Data stored for these attributes may be quantitative (e.g.,an amount) and/or qualitative (e.g., name of merchant). In someembodiments, metadata may also be stored. A ledger inquiry and updateinterface 212C may be one or more of an application, application programinterface, software, hardware, server, or protocol that allows theaddition of data (e.g., a new attribute or a detail regarding anattribute for the payment transaction) to a blockchain and/or sharedledger. In some embodiments, ledger inquiry and update interface 212Cmay further enable the access or retrieval of data for any attribute ofthe transaction information from the shared ledger.

FIG. 3 depicts a simplified sequence flow diagram of method forestablishing loyalty points payment system using blockchain, inaccordance with one non-limiting embodiment. In an example embodiment,the method may be executed by the processors, devices, and/or componentsrelated to the consumer 102, the issuer 116, the blockchain loyaltypoints payment system (“blockchain server”) 112, the payment networkserver 114, the acquirer 108, and the merchant 106.

In process flow 302, issuer 116 may issue a loyalty card to consumer102. For example, issuer 116 may be a casino which issues a loyalty cardto a consumer allowing the consumer to play games at the casino orpurchase items with the issued loyalty cards. In process flow 304,issuer 116 or a consumer 102 may send a request to add points to theloyalty card associated with the consumer 102 to acquirer 108. Theprocess of adding points to the loyalty card may include causingacquirer 108 to receive, over a wired or wireless network, a request toadd loyalty points to the loyalty card by at least one of consumer 102or issuer 116, wherein the request includes at least one of a consumer'saccount identification, an account identification, an issueridentification, and a number of points to be added to the loyalty card.The acquirer 108 identifies a network node maintaining a distributedledger associated with issuer 116 according to the received issueridentification and the account identification.

The acquirer 108 may prompt participants of a distributed ledger tovalidate whether loyalty points can be added to the identified account.Additionally, if all of the participants of the shared ledger accept therequest, acquirer 108 may generate a new immutable entry to theblockchain associated with issuer 116. The generated blockchain entrymay include at least one of a public key identifying the consumer, aunique private key, total sum of loyalty points after adding requestedafter adding requested loyalty points, and terms and conditionassociated with the points. The acquirer 108 may send an approvalmessage to the point of sale system at merchant 106 once the distributedledger node(s) approves the transaction.

In an above example embodiment, the consumer may add loyalty points tothe loyalty card by at least one of earning loyalty points by purchasinggoods or services provided by issuer 116, transferring funds from one ormore financial institutions 110 to the loyalty card, and transferringpoints from another account. In accordance with the above embodiment,the terms and condition associated with the account are at least one ofspending limits on the account, marking points as spendable withspecific merchants, and rules and regulations accordingly to thepolicies of the issuer 116. At process flow 306, issuer 116 may reportthe loyalty points (LP) associated with loyalty points card of consumer102 to blockchain server 112. In yet another embodiment, the terms andconditions associated with the points may be at least one or morespending limits on a consumer's account, marking points as spendablewith specific merchants, and rules and regulations accordingly topolicies of issuer 116.

In an example embodiment, as described in operation 318, issuer 116 mayrequest to settle pending transactions to acquirer 108. The request mayinclude at least one of an issuer's account information and routinginformation associated with a financial institution. In anotherembodiment, acquirer 108 may query blockchain server 112 for any one ormore unsettled transactions, as per operation 320. In the above exampleembodiment, the acquirer may receive a list of unsettled transactionsfrom blockchain server 112 in operation 322.

Once the pending transactions are identified in operation 320, theacquirer may determine a payment amount to be transferred for settlementbetween issuer 116 and merchant 106 using conversion informationavailable on at least one distributed ledger entry associated with theat least one pending transaction(s). In the above embodiment, inoperation 324, acquirer 108 may further send a request to one or morefinancial institutions 110 to transfer the determined payment amountfrom an issuer's account to a merchant's account using a standardpayment process for the at least one pending transaction(s) usingpayment networks server 114.

In operation 308, the consumer may offer points (e.g., via a loyaltycard) for purchase at a point of sale of merchant 106. In operation 310,the point of sale of merchant 106 may send an authorization request toacquirer 108. The acquirer 108 may receive a consumer's accountidentification, an issuer identification, and transaction informationfor a transaction from a point of sale system as part of a request forauthorization for transaction at process 310. The transaction in process310 may be at least one of an online and/or in-store purchase of good(s)or service(s).

The acquirer processor 108 may identify a network node maintaining ablockchain network associated with the issuer and a consumer blockchainentry according to received issuer and consumer's accountidentification. Two or more issuers can but need not have nodes in thesame blockchain network. It is contemplated that the debit network mayhave nodes in multiple blockchain networks. For example, acquirer 108may convert a transaction dollar amount to loyalty points according to aconversion formula in the identified consumer blockchain entry. Atoperation 312, acquirer 108 may prompt participants of a shared ledger(e.g., 212C of blockchain server 112) to validate whether the consumerblockchain entry has the requisite loyalty points for the transaction.In an example embodiment, the blockchain entry may be accessible by atleast one of the participants of the shared ledger and acquirer 108. Theat least one participant of the shared ledger may maintain differentblockchain(s) on a network node maintained by a different issuerparticipating in a loyalty program. In an example embodiment, theblockchain entry may comprise at least one of a public key identifyingthe consumer, a unique private key, a header, loyalty points to currencyconversion table, transaction information and content data. In anexample embodiment, the distributed ledger entry may comprise at least aunique identifier of the consumer, a header, conversion informationbetween points and currency (i.e., rate at time of conversion),transaction information, and content data.

In one embodiment, acquirer 108 may generate a new immutable entry tothe blockchain for the transaction with remaining loyalty points in theloyalty card after deducting the loyalty points required for thetransaction if all of the participants of the shared ledger accept thetransaction. The acquirer 108 may send a transaction approval message topoint of sale system at merchant 106 once the transaction is approved.In some embodiments, acquirer 108 and/or the blockchain loyalty pointspayment system may encrypt the transaction information using, e.g., anencoder. The encryption may protect sensitive information of theconsumer or merchant, and/or restrict the accessibility of theinformation. The attributes of the payment transaction may include, butare not limited to, e.g., an identification of the merchant, anidentification of the consumer, the transaction amount, an itemizationof the goods and/or services transacted for, geographical and/ortemporal information of the transaction, any taxes, any tips, anydiscounts; any fees directed towards acquirers, issuers, paymentnetworks; etc.

In some embodiment, the acquirer 108 may receive a rejection messagefrom the blockchain server 212 (e.g., ledger inquiry and update server212C) if the consumer 102 does not have required loyalty points for thetransaction. The acquirer 108 may send the rejection message to thepoint of sale system of merchant 106. In an alternative embodiment, upondetermining that consumer 102 does not have required loyalty points forthe transaction, acquirer 108 may further send available dollar amountin the loyalty card to point of system of merchant 106. The point ofsystem may present consumer 102 the dollar amount available in theloyalty card on an interactive graphical user interface (GUI). Theacquirer 108 may further provide the point of sale system at merchant106 an option to choose partial payment using available loyalty points.The point of sale at merchant 106 may be a participant of loyaltyprogram or issuer 116 of the loyalty card. In an alternative embodiment,merchant 106 may not be part of loyalty program nor the issuer 116 ofthe loyalty card.

The acquirer 108 may update the loyalty points associated with theconsumer's account identification in an issuer database 202B upon theapproval of the transaction from the shared ledger. Additionally, theloyalty points at issuer database 202B may be accessed by at least oneof consumer 102 and issuer 116 using interactive graphical userinterface (GUI). In an example embodiment, acquirer 108 may be anobserver of the blockchain and/or a participant of its shared ledger.

In some embodiments, ledger inquiry and update interface 212C may enablethe access or retrieval of information from the shared ledger. Thus, theledger inquiry and update interface may respond to requests to addattributes of loyalty points payment transaction and/or search for orretrieve details regarding a transaction attribute. The ledgers and/orsubledgers of the blockchain loyalty points payment system may becontinually updated, and may be updated to reflect accurate detailsregarding the payment transaction between participants of theblockchain. The ledger may be updated and/or new details may be postedby adding blocks to the blockchain using pre-defined rules, e.g., agreedon by the participants of the blockchain. In other embodiments, theledger may be updated and/or new details may be posted, using blockchain mining methods known to persons having skill in the art.

FIG. 4 is an exemplary structure of a blockchain entry, according to oneor more non-limiting embodiments. In one embodiment, blockchainstructure may comprise one or more block entries (e.g., 410 and 430). Ablockchain entry 410 structure may comprise a header and contentportion, as shown in FIG. 4 . The header may include unique blockchainentry ID and Nonce. The “nonce” in a bitcoin block may be a 32-bit(4-byte) field whose value is set so that the hash of the block willcontain a run of leading zeros. Nonce may be a random arbitrary numberthat is only used once. The blockchain header may also contain previousblock entry identification. The second portion of the blockchain entry'scontent may include information, such as consumer identification,transaction detail, points dollar conversion chart, digital sign of theconsumer, merchant identification, etc.

FIG. 5 depicts block-diagram showing loyalty points payment systeminvolving multiple issuers. In an example embodiment, issuer 1 (502) maybe a merchant selling goods, issuer 2 (504) may be a casino providinggaming machines and services, and issuer 3 (506) may be a merchantselling services. The issuers 502, 504, and 506 may issue separateloyalty points memberships to one or more consumers or patrons. Theissuers 502, 504, and 506 may mine their own blockchain servers and actas shared ledger to approve and verify transactions involving loyaltypoints. For example, payment transaction involving loyalty points issuedby issuer 2 (504) may be approved by issuer 1 (502) and issuer 3 (506).

In one embodiment, the issuers (502, 504, and 506) may be part ofloyalty points payment system using blockchains and issue a loyalty cardthat is compatible with issuers participating in the distributed ledgerpayment program. In some embodiments, consumer or patron may play gamesat the casino using the loyalty card and earn points. The acquirer 516may request a new blockchain entry to blockchain server 510 afterinquiring with block chain servers 508 and 512. Similarly, the patronmay use the loyalty points at the casino after inquiring transactionwith shared ledger (e.g., 508 and 512).

In another embodiment, the consumer or card member may use the loyaltycard at merchant 520, where the acquirer may act as an observer thatqueries the blockchain servers 508, 510, and 512 for transactionapproval and converts the purchase amount into points according toconversion formula provided by the entry into the blockchain network orits distributed ledger. These arrangements may enable the patron to usethe loyalty points earned from casinos to a merchant 520 for paymenttransactions in an efficient and secure manner without requiring themerchant 520 to be aware of available loyalty points or loyalty pointsconversion. The merchant 520 may be paid the transaction amount from thecasino's account at financial institution 518 during settlement processtriggered by the acquirer 516.

In various embodiments of the present disclosure, attributes of thepayment transaction may refer to, for example, details related to apayment transactions (e.g., an identification of the merchant, anidentification of the consumer, the transaction amount, an itemizationof the goods and/or services transacted for, geographical and/ortemporal information of the transaction, any taxes, any tips, anydiscounts; any fees directed towards acquirers, issuers, paymentnetworks; currency exchange rates; etc.). In such embodiments, theresults and/or process of the transaction(s) may be published in theblockchain or its distributed ledger, which may be readily available tothe participants of the blockchain (e.g., issuer, acquirer, consumer,merchant, etc.).

FIGS. 6A-6B depict block diagrams of general methods 600 and 650 forusing a debit network as an intermediary between distributed ledgers. Itis contemplated that at least some embodiments of the loyalty pointspayment system utilize the method described in FIGS. 6A-6B. Furthermore,while FIG. 6A may depict an exemplary embodiment where a debit networkserves merely an intermediary, FIG. 6B may depict an exemplaryembodiment where a debit network may also serve as a member of at leasttwo blockchain networks (and their respective distributed ledgers).

Thus, for both FIGS. 6A and 6B, at step 602, a first blockchain networkand/or its distributed ledger (e.g., “distributed ledger A”) may receivetransaction information, e.g., pertaining to a payment transactionoriginating at a merchant. For example, this transaction may beinitiated by a consumer at a merchant (e.g., casino) for the purchase ofa good or service, for currency, cryptocurrency, or tokens (e.g.,loyalty points). The received transaction information may includeidentifiers of various parties of the transaction, e.g., merchant,consumer, acquirer, issuer, etc. The received transaction informationmay further include the requisite amount of the currency,cryptocurrency, or tokens for the transaction. In some embodiments, thereceived transaction information may also include, e.g., a descriptionor identification of the requested good or service, fraud information,configuration plans for loyalty points, etc. The transaction informationmay be received from a computing system, processor, and/or server of oneor more participants of the transaction (e.g., consumer, issuer,merchant, acquirer, etc.), a POS system of a merchant or acquirer, aserver pertaining to the system for using the debit network as anintermediary for distributed ledger, and/or a third party.

Referring to FIG. 6A, at step 604A, the blockchain network or server fordistributed ledger A may process the received transaction and determinewhether the received transaction information is intended for a partythat is not a member of the blockchain network (or distributed ledger)A. If it is determined that the received transaction information isintended for a party that is not a member of the blockchain network (ordistributed ledger) A, step 604A may further include relaying all or atleast some of the transaction information to debit network 614A. Therelayed transaction information may include, for example, theinformation intended for the party that is not a member of blockchainnetwork A 612A (or its distributed ledger).

Debit network may serve as an intermediary for two or more blockchainnetworks and/or their distributed legers. Each blockchain network and/ortheir distributed ledgers may serve a function or role for paymenttransactions, and/or may comprise of different sets of transactionparticipants. Debit networks may be integrated into blockchain networksby having a node in a blockchain network. In some embodiments, debitnetworks can also be integrated into blockchain networks by having theparticipants in the transaction be a member of the blockchain networkand those participants communicating both with the blockchain and withthe debit network.

At step 606A, debit network may identify the intended party in therelayed transaction information and locate the blockchain network (orits distributed ledger) in which the intended party is a member (e.g.,blockchain network B 616A or its distributed ledger). Step 606A mayfurther include further relaying at least some or all of the previouslyrelayed transaction information to the located blockchain network (orits distributed ledger) in which the intended party is a member (e.g.,blockchain network B 616A or its distributed ledger).

At step 608, blockchain network B 616A (or its distributed ledger) mayuse the relayed transaction information to perform a specific function.For example, blockchain network B may record the completion of thetransaction using the relayed transaction information. The recordationinto the distributed ledger may be performed e.g., using a consensusmechanism involving participants of blockchain network B. In oneembodiment, the completion of the transaction may involve, for example,the recordation of the transfer of currency, cryptocurrency, or tokens(e.g., loyalty points) between two or more participants of thetransaction. Alternatively or additionally, the specific function atblockchain network B may be a transfer of a currency, cryptocurrency,and/or tokens (e.g., loyalty points) that is distinct from a transfer ofa currency, cryptocurrency, and/or tokens (e.g., loyalty points) thatmay be performed at blockchain network A. For example, in blockchainnetwork B, a distributed ledger may record the transfer and/or use ofloyalty points used for a purchase at a merchant, according to methodsdescribed in the present disclosure. In such an example, in blockchainA, a distributed ledger may record the appropriate funds transferred tothe merchant from a casino or loyalty points provider based on aconversion formula of currency to and from loyalty points, according tomethods described herein. It is contemplated that in some embodiments,the roles played by blockchain A and B may be reversed. Once blockchainnetwork B fulfils its function, it may transmit updated transactioninformation to debit network 614A.

Subsequently, at step 610, debit network may relay the updatedtransaction information to blockchain network A 612A (or its distributedledger). The updated transaction information may prompt blockchainnetwork A 612A (or its distributed ledger) to serve another function,for example, finalizing a recording (e.g., consensus) on the distributedledger. In one embodiment, the updated transaction information receivedfrom blockchain network B may include the recorded transfer and/or useof loyalty points for a transaction originating at a merchant. In suchan embodiment, at blockchain network A, a distributed ledger may recordthe transfer of the appropriate funds (in currency or cryptocurrency)that is commensurate with the transfer and/or use of loyalty points tothe merchant.

FIG. 6B may depict an exemplary embodiment where a debit network mayalso serve as a member of at least two blockchain networks (and theirrespective distributed ledgers). Thus, at 604B, the blockchain network A612B may process the received transaction and determine whether thereceived transaction information is intended for debit network 614B.However, debit network 614B may also be a member of blockchain network B(and its distributed ledger). If it is determined that the receivedtransaction information is intended for debit network 614B, then debitnetwork 614B may receive all or at least some of the transactioninformation received from step 602.

In such embodiments, while debit network 614B may serve as anintermediary for two or more blockchain networks and/or theirdistributed legers, debit network 614B may also be a member of the twoor more blockchain networks. Thus, at least in some embodiments, debitnetwork 614B may readily receive or transmit information intended foreither blockchain network via their shared ledgers. Each blockchainnetwork and/or their distributed ledgers may serve a function or rolefor payment transactions, and/or may comprise of different sets oftransaction participants.

At step 606B, being also a member of blockchain network B, debit network614B may relay or distribute at least some or all of the receivedtransaction information from blockchain network A 612A (or itsdistributed ledger) to blockchain network B 616B (or its distributedledger). Thereafter, in some embodiments, steps 608 and 610 may beperformed, as described above.

These and other embodiments of the systems and methods may be used aswould be recognized by those skilled in the art. The above descriptionsof various systems and methods are intended to illustrate specificexamples and describe certain ways of making and using the systemsdisclosed and described here. These descriptions are neither intended tobe nor should be taken as an exhaustive list of the possible ways inwhich these systems can be made and used. A number of modifications,including substitutions of systems between or among examples andvariations among combinations can be made. Those modifications andvariations should be apparent to those of ordinary skill in this areaafter having read this disclosure.

It is intended that the specification and examples be considered asexemplary only, with a true scope and spirit of the invention beingindicated by the following claims.

1-20. (canceled)
 21. A computer-implemented method for using a debitnetwork as an intermediary between distributed ledgers, the methodcomprising: receiving, at a first blockchain network from a point ofsale of a merchant, transaction information comprising at least atransaction amount in resources of a first type, wherein a debit networkis a participant of the first blockchain network; sending, over a wiredor wireless network, the transaction information to the debit network;identifying, using the debit network, a second blockchain network usingthe transaction information, wherein the debit network is a participantof the second blockchain network; converting, using the secondblockchain network, the transaction amount in resources of the firsttype to an amount of resources of the second type; and sending, by thedebit network, an updated transaction information indicating the changein the resources of the second type to the first blockchain network. 22.The method of claim 21, further comprising, sending, by the firstblockchain network, a transaction approved message to the point of salesystem at the merchant.
 23. The method of claim 21, wherein thetransaction information further comprises at least a consumeridentification and an issuer identification from a payment vehiclepresented for a transaction of a good or service, and wherein themerchant and/or its acquirer are participants that access the firstblockchain network and the second blockchain network is accessed by theconsumer and/or the issuer as participants.
 24. The method of claim 21,further comprising: determining whether all of the participants of thesecond blockchain network accept the transaction; upon determining thatall of the participants of the second blockchain network accept thetransaction, generating a new immutable entry to a shared ledger of thesecond blockchain network indicating a change in the resources of asecond type for one or more participants of the transaction; andsending, over a wired or wireless network, an updated transactioninformation indicating the change in the resources of the second type tothe debit network.
 25. The method of claim 24, further comprising:prompting, to participants of the second blockchain network, to validatewhether a consumer has a required amount of resources of the second typefor the transaction.
 26. The method of claim 25, wherein the resourcesof the first type comprises an amount in a currency or cryptocurrency,and the resources of the second type comprises loyalty points.
 27. Themethod of claim 25, wherein the new immutable entry includes at leastone of a public key identifying the consumer, a unique private key, asum of loyalty points after adding requested loyalty points, and termsand condition associated with the points.
 28. The method of claim 21,further comprising, if all of the participants of the first blockchainnetwork accept the updated transaction, prompting, to participants ofthe first blockchain network, to validate whether one or moreparticipants of the transaction has a required amount of resources ofthe first type for the transaction.
 29. The method of claim 28, furthercomprising, generating a new immutable entry to a shared ledger of thefirst blockchain network indicating a change in the resources of thefirst type for one or more participants of the transaction.
 30. Themethod of claim 23, wherein the participants of the transaction includesone or more of: the consumer, the merchant, the issuer, or the acquirer.31. The method of claim 23, wherein the payment vehicle presented forthe transaction of the good or service identifies the issuer and anaccount for one or more of the resources of the first type or resourcesof the second type belonging to the consumer.
 32. The method of claim23, further comprising, prior to receiving transaction information froma point of sale of a merchant: issuing, by the issuer, a payment vehicleto the consumer for acquiring resources of the second type, wherein thepayment vehicle is at least one of physical card and digital cardcompatible to the debit network or the second blockchain network; addingresources of the second type to the payment vehicle by at least one ofthe consumer or the issuer; generating, via a wired or wireless network,a blockchain entry to the second blockchain network, wherein theblockchain entry includes resources of the second type to be added andterms and condition associated with the resources of the second type;and reporting the amount of resources of the second type to a sharedledger of the second blockchain network.
 33. The method of claim 23,wherein the issuer identification from the payment vehicle identifiesone or more of: (1) an account of the consumer for acquiring ordeducting resources of the first type, and (2) the account of theconsumer for acquiring or deducting resources of the second type.
 34. Adecentralized computer system for using a debit network as anintermediary between distributed ledgers, the system comprising: a datastorage device storing instructions for processing a transaction usingone or more blockchain networks; two or more distinct blockchainnetworks; a debit network; and a processor configured to execute theinstructions to perform a method including: receiving, at a firstblockchain network from a point of sale of a merchant, transactioninformation comprising at least a transaction amount in resources of afirst type, wherein the merchant and/or its acquirer are participantsthat access the first blockchain network and a debit network is aparticipant of the first blockchain network; sending, over a wired orwireless network, the transaction information to the debit network;identifying, using the debit network, a second blockchain network usingthe transaction information, wherein the debit network is a participantof the second blockchain network; converting, using the secondblockchain network, the transaction amount in resources of the firsttype to an amount of resources of the second type; and sending, by thedebit network, an updated transaction information indicating the changein the resources of the second type to the first blockchain network. 35.The system of claim 34, wherein the processor is further configured for:sending, by the first blockchain network, a transaction approved messageto the point of sale system at the merchant.
 36. The system of claim 34,wherein the transaction information further comprises at least aconsumer identification and an issuer identification from a paymentvehicle presented for a transaction of a good or service, and whereinthe merchant and/or its acquirer are participants that access the firstblockchain network and the second blockchain network is accessed by theconsumer and/or the issuer as participants.
 37. The system of claim 36,wherein the processor is further configured for: prompting, toparticipants of the second blockchain network, to validate whether theconsumer has a required amount of resources of the second type for thetransaction.
 38. The system of claim 34, wherein the processor isfurther configured for, if all of the participants of the firstblockchain network accept the updated transaction: prompting, toparticipants of the first blockchain network, to validate whether one ormore participants of the transaction has a required amount of resourcesof the first type for the transaction.
 39. The system of claim 38,wherein the processor is further configured for: generating a newimmutable entry to a shared ledger of the first blockchain networkindicating a change in the resources of the first type for one or moreparticipants of the transaction.
 40. A non-transitory machine readablemedium storing instructions that, when executed by a processor, causesthe processor to perform a method for using a debit network as anintermediary between distributed ledgers, the method including:receiving, at a first blockchain network from a point of sale of amerchant, transaction information comprising at least a transactionamount in resources of a first type, wherein a debit network is aparticipant of the first blockchain network; sending, over a wired orwireless network, the transaction information to the debit network;identifying, using the debit network, a second blockchain network usingthe transaction information, wherein the debit network is a participantof the second blockchain network; converting, using the secondblockchain network, the transaction amount in resources of the firsttype to an amount of resources of the second type; and sending, by thedebit network, an updated transaction information indicating the changein the resources of the second type to the first blockchain network.